<?php
/**
 * <https://y.st./>
 * Copyright © 2016 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'The GT-i9100M runs Replicant!',
	'body' => <<<END
<p>
	We began the day by moving furniture outside.
	We were going to rent a moving van, but my mother decided to take the minivan instead.
	We got three minivan loads of stuff into the storage unit, much of which was shelves and tables, so we can stack boxes on them later.
</p>
<p>
	On one trip, on the way to the storage unit, my mother stopped at the post office.
	If they&apos;d let me know, I could have brought the GT-i9100G with me so I could get that sent back as well, but I&apos;m never kept in the loop on these things.
	Our goal in going there was to check on the security deposit refund check supposedly sent by the landlords, but the landlords said that the post office was refusing to deliver it.
	It turns out that the check had somehow been caught in the mail after all, though the postal worker was able to easily retrieve it for us.
	They claimed that the envelope had been all over the country, visiting all the wrong Springfields.
	They said that there are seven Springfields in the United States and that the machines can&apos;t read print.
	THe postal worker showed us at the bottom of the envelope where machines had added several barcodes on top of one another, each denoting a different Springfield that it&apos;d visited.
	I found this hard to believe though, and it looked to me like the machines had put the same barcode in the same place several times, blurring it beyond machine recognition.
	If there was an issue with the address, I don&apos;t think that it was that there are too many Springfields (though I&apos;m not denying that there are in fact too many Springfields).
	Just as a side note, there are actually far more than seven <a href="https://en.wikipedia.org./wiki/Springfield#United_States">Springfields in the United States</a>.
	While we were there, I asked about my $a[ID] card, which was supposed to arrive in the mail about two months ago.
	The postal worker blamed the $a[DMV], saying that anyone that&apos;s moved in the past four months and updated their address on file with the $a[DMV] has been experiencing this issue.
</p>
<p>
	The GT-i9100M arrived today; both the sticker behind the battery and the boot screen confirmed that it is indeed the GT-i9100M.
	Finally, someone sent me the device that I actually paid for.
	I had read somewhere that the GT-i9100M might not install the custom recovery correctly without first installing the Samsung-provided update, which alters not only the system but also the bootloader, so I tried to update the device.
	The device said that no update is available, so I assume that the update had already been installed by the previous owner; this is, after all, a second-hand device.
	I tested the back camera, which seemed to work well.
	After that, I proceeded with the <a href="https://redmine.replicant.us/projects/replicant/wiki/GalaxyS2I9100Installation">installation</a>.
	After installing the custom recovery, the device rebooted with large yellow warning triangle - hilarious! On the GT-i9300, only a tiny red exclamation point was added to the upper left corner of the screen.
	Strangely though, the text stating that the device is a GT-i9100M changed as well, now saying that the device is a regular GT-i9100.
	After installing Replicant as well, the device greeted me with the familiar Replicant loading image.
	Everything seems to work well.
	Fantastic! I tested the camera again too, which also seems to work well, making it more likely that my last Replican&apos;t camera was borked by water damage as I had thought and less likely that it was borked by a software update as I&apos;d feared.
	I set my new $a[PIN] (which is now eleven digits long), turned on Privacy Guard, and started the device storage encryption process.
	While device encryption was starting, I put on the bad screen protector and bad case that I had ended up with due to an incorrect product-listing page.
	The screen protector has small bubbles underneath it that I can&apos;t seem to get rid of and the case needed hole poked in it to get a lanyard through to the device itself, as the GT-i9100M (and the GT-i9100) has a nice lanyard hole built in, but the case covers it up.
	I set up a stretchy, spiral cord from the lanyard to my belt loop, so that I can&apos;t walk off without my device in the future.
	Quite a while after, the device finished encrypting the internal storage, so I looked up the <a href="https://www.cricketwireless.com./support/apps-and-services/bring-your-own-device-byod/customer/bring-your-own-android.html">$a[APN] settings</a> to use and set up the $a[APN].
	I forgot that Replicant has F-Droid installed by default and started to download it to install ...
	A few seconds later, I remembered and canceled the download.
	I don&apos;t know why orWall quit working on the GT-i9300, but it works just fine on the GT-i9100M.
	orWall seems to have an updated interface though, so maybe some new update fixed the problem with orWall&apos;s init script, which previously, wasn&apos;t successfully initializing iptables.
	Furthermore, KeePassDroid now seems to default to a file name reflecting that a KDBX database is being used; KeePassDroid is now KDBX-compatible! It still accepts the older KDB database files, so I can still keep it in sync with my laptop, but when Debian 9 hits, I can safely update my database on both devices.
	GApps Browser doesn&apos;t render as well on Replicant though.
	Unfortunately, I need it for outgoing calls and $a[SMS].
	I don&apos;t plan to use those with my Google Voice number often, but on the rare occasion that I do, it&apos;s going to be a bit of a pain.
	$a[MTP] on this device doesn&apos;t seem to work as well as on the GT-i9300, and even after formatting the $a[SD] card as an Ext4 card, the mobile was trying to store things on it using $a[FAT].
	I ended up needing to transfer the files to the $a[SD] card from my laptop directly, instead of over $a[MTP].
	After that, the device was able to read the music files, so I&apos;m hoping that further writes to the card will be done using the actual file system of the card.
	It&apos;s worth noting that after Replicant had written to the card in $a[FAT] mode (rejecting any file with a name that $a[FAT] couldn&apos;t handle), my laptop couldn&apos;t even see the files, as they hadn&apos;t been written correctly.
	Lastly, this device is missing an indicator $a[LED].
	It took me a while to figure out that it wasn&apos;t that the indicator led wasn&apos;t lighting up, but that it outright didn&apos;t exist.
	The thing that I&apos;d been staring at was the front camera; when unlit, the indicator $a[LED] would have been invisible.
	No longer will I be able to glance at the device from across the room and see if it&apos;s done charging.
</p>
<p>
	My mother has a job interview tomorrow in Estacada.
	Hopefully, they&apos;ll get the job.
	While they&apos;re out though, I&apos;ll have the opportunity to finally send back the GT-i9100G and speak to the $a[DMV] about my missing $a[ID] card.
</p>
END
);
